⚠️ Next.js 16.2.10 - Tests need review#51
Conversation
- Updated Next.js to 16.2.10 - Bumped package version to 16.2.10 - Memory tests: success - Redis tests: failure Co-Authored-By: GitHub Actions <github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Code Review
This pull request updates the 'next' dependency from '^16.2.9' to '^16.2.10' across several packages and applications in the monorepo, along with bumping the version of '@mrjasonroy/cache-components-cache-handler' to '16.2.10'. However, the reviewer noted that 'apps/redis-example/package.json' was missed in this update, resulting in a version mismatch that should be resolved.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| "@mrjasonroy/cache-components-cache-handler": "workspace:*", | ||
| "ioredis": "^5.4.1", | ||
| "next": "^16.2.9", | ||
| "next": "^16.2.10", |
There was a problem hiding this comment.
The Next.js version was updated to ^16.2.10 here and in apps/legacy-cache-test/package.json, but apps/redis-example/package.json was missed and is still using ^16.2.9 (as seen in pnpm-lock.yaml). This version mismatch in the monorepo is likely the cause of the Redis cache test failures, as apps/redis-example is not aligned with the rest of the workspace. Please update apps/redis-example/package.json to use ^16.2.10 as well.
Next.js 16.2.10 Release
📦 Package version will be bumped to 16.2.10
Changes
Test Results
Auto-generated by nextjs-version-check workflow